fix(server): settle snoozed threads immediately - #5379

Note

Low Risk
Localized orchestration decider lifecycle behavior with new unit tests; no auth, data migration, or broad API surface changes.

Overview
Settling a thread now clears snooze so the row can show as Settled instead of staying under Snoozed when lifecycle classification prefers snooze over settled.

The thread.settle handler in decider.ts builds companion events for anything that would keep the row pinned or snoozed: it still emits thread.unpinned when pinned, and also emits thread.unsnoozed with reason user when snoozedUntil is set. Awake threads still get only thread.settled. Pinned + snoozed threads get settled, unpinned, and unsnoozed in one command.

Tests in decider.settled.test.ts cover snoozed settle, legacy settled-and-still-snoozed repair on repeat settle, and pinned+snoozed combinations.

^{Reviewed by Cursor Bugbot for commit 5a3fd32. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix thread settling to immediately unsnooze snoozed threads

• When settling a thread, decider.ts now emits thread.unsnoozed (with reason 'user') alongside thread.settled when the thread is snoozed.
• A pinned thread still emits thread.unpinned; both companion events can now be emitted together in the sequence [thread.settled, ...companions].
• Behavioral Change: previously, settling a snoozed thread left the snooze state intact; now it is cleared as part of the same operation.

^{Macroscope summarized 5a3fd32.}